Vibe Coding Beginner's Experience - Antigravity

TLDR

• Antigravity is a development tool built on Code OSS, suitable for developers accustomed to VS Code.
• Quotas are calculated separately from the web version of Gemini, but different models consume quotas at different weights.
• It is recommended to set the Request Review permission to prevent the Agent from automatically executing high-risk commands.
• Global or project-level background information and behavioral guidelines can be defined via the GEMINI.md file.
• Always inspect the code and scripts generated by the Agent to avoid encoding errors, residual files, or technical debt.
• Utilize the Agent for repetitive file migrations or batch operations, but keep core logic and Git operations under human supervision.

---

Antigravity Core Mechanisms and Settings

Antigravity is a development environment built on Code OSS, with an operational logic highly similar to VS Code.

Quota Management and Monitoring

Antigravity's quota pool is calculated separately from the web version of Gemini. By installing the Antigravity Cockpit extension, developers can monitor the remaining quotas for each model in real-time at the bottom right corner.

WARNING

Although a single Quota Group contains multiple models, this does not mean that the weight of quota consumption is the same for different models within the same group.

Permissions and Behavioral Control

To ensure development security, it is recommended to adjust permissions in Settings => Open Antigravity User Settings based on the nature of the project:

• Review Policy: It is recommended to set this to Request Review to ensure that the AI requires human confirmation before executing plans.
• Browser Tools: If financial transactions or external integrations are involved, JavaScript execution permissions should be set to Request Review; for purely static websites, it can be set to Always Proceed.
• Conversation Mode: It is recommended to use Planning mode, allowing the Agent to generate an execution plan first to avoid uncontrollable risks caused by direct execution.

Agent Memory Settings (GEMINI.md)

By creating a GEMINI.md in the project directory, you can force the Agent to reference specific background information and guidelines. Its inheritance rules are as follows:

• More specific files take precedence: Files in subdirectories will overwrite or supplement the content of parent directories.
• Loaded from near to far: The Agent will search layer by layer from the current working directory up to the project root directory.

TIP

This feature is commonly used to lock in Commit conventions, ensuring that the Commit Messages generated by the Agent comply with project standards.

---

Practical Application Scenarios and Tips

File Migration and Automation

Antigravity excels at handling "not difficult but tedious" tasks, such as:

• Image Migration: Use commands to ask the Agent to check Markdown links, download images to a specified folder, and batch replace the links.
• Framework Conversion: Use the Agent to read change history and titles to automatically generate Frontmatter that complies with VitePress or Jekyll standards for a large number of Markdown files.
• API Batch Operations: Write scripts to call external APIs (such as the HackMD API) for bulk content updates.

Browser Automated Testing

Through the Antigravity Browser Control extension, the Agent can read the DOM for End-to-End testing.

• Under what circumstances will this problem be encountered: When cross-page or style checks are required, the Agent may produce misjudgments because it cannot accurately determine RWD styles.
• Note: This feature will additionally call the Gemini Flash model, which will incur additional quota consumption.

---

Troubleshooting and Technical Recommendations

When using Vibe Coding mode, developers should pay special attention to the following potential risks:

1. Git Snapshot Conflicts

• Under what circumstances will this problem be encountered: If the developer manually modifies files via Git while the Agent is executing a task, it may cause the Agent to overwrite changes using an older snapshot.
• Recommendation: Avoid performing Git operations while executing AI tasks.

2. Encoding and Script Preference Issues

• Under what circumstances will this problem be encountered: The Agent prefers using Python or PowerShell for batch tasks. If the encoding method is not specified, it is easy for Chinese content to become garbled.
• Recommendation: Explicitly request the use of encoding-safe (e.g., UTF-8) methods for file processing in your instructions.

3. Residual Files and Technical Debt

• Under what circumstances will this problem be encountered: Temporary scripts or text files generated by the Agent during task execution are easily committed into the repository by mistake if not cleaned up.
• Recommendation: Set up an ignore list in .gitignore and manually review the code after development is complete to avoid "disposable code" that lacks maintainability.

4. Hallucinations and Semantic Understanding Limitations

• Under what circumstances will this problem be encountered: When asking the Agent to perform batch content conversion (e.g., converting Mainland terminology to Taiwan terminology), if it is not asked to read the full text first, it may lead to semantic misjudgment.
• Recommendation: Avoid using Fast mode for complex logic; you should require the Agent to read the context before making judgments.

---

Change History

• 2026-01-07 Initial document creation.
• 2026-01-08 Added scope, inheritance relationships, and testing methods for GEMINI.md.
• 2026-03-13 Added information regarding Google's adjustment of the Antigravity quota mechanism on 2026-03-12.